home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
sx405a.zip
/
SAPPHTS.DOC
< prev
next >
Wrap
Text File
|
1992-10-06
|
29KB
|
608 lines
█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
█ HOW TO USE THIS TROUBLE-SHOOTING GUIDE █
█──────────────────────────────────────────────────────────────────────────────█
█ █
█ This guide is contained in the file SAPPHTS.DOC. You can print it out, but █
█ it works best if you view it via the SYSOP menu, which uses our SEE program. █
█ To do that, enter SYSOP at the DOS prompt, select INFO, then select TROUBLE. █
█ This lets you search the guide for keywords whenever you have a problem. █
█ █
█ Each problem described in this file is preceded by a list of keywords, each █
█ of which is preceded by a slash character (/). Thus, if you had a modem █
█ problem, you could press "F" (for Find) then search for /MODEM. By repeat- █
█ edly searching for /MODEM (press F3 after the initial search) you can █
█ quickly scan the file for any related problems. █
█ █
█ When in doubt about which keyword to choose, use the shortest one that can █
█ describe your problem. For example, if a user has trouble connecting, look █
█ for /CONNECT rather than /CONNECTION PROBLEM, since /CONNECT would match on █
█ /CONNECT or /CONNECTING or /CONNECTION and so on. Most important, avoid any █
█ plurals: search for /MODEM, not /MODEMS. █
█ █
█ You can also search major categories. See the INDEX section, below. █
█▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
████████████████████████████████████████████████████████████████████████████████
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
█░▒░▒░▒░▒░▒░▒▌ == INDEX == ▐▒░▒░▒░▒░▒░▒░█
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
████████████████████████████████████████████████████████████████████████████████
Major categories in this guide are presented in alphabetical order, as
follows:
■ COMMANDS (STANDARD)
■ COMMANDS (SYSOP)
■ DISPLAY
■ DOORS
■ EVENTS
■ FILE TRANSFER
■ FRONT END
■ INPUT
■ MAINTENANCE
■ MESSAGES
■ MODEM
■ NOISE
■ PROGRAM FAILURE
Specific headings are preceded by two equals signs and a blank (see INDEX
heading, above). Thus, to find the NOISE section, press F for Find, type
"==", then a blank, then "NOISE".
████████████████████████████████████████████████████████████████████████████████
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
█░▒░▒░▒░▒░▒░▒▌ == COMMANDS (STANDARD) == ▐▒░▒░▒░▒░▒░▒░█
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
████████████████████████████████████████████████████████████████████████████████
KEYWORD: /COMMANDS/SET/NAMES/TEXT
PROBLEM: How do SET, NAMES or TEXT work?
These commands "tune" other commands to restrict or control what they report.
SET controls them by time, NAMES by the name of the person or file being
referenced, and TEXT by any text (apart from name-oriented text) that might
be presented by the command.
████████████████████████████████████████████████████████████████████████████████
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
█░▒░▒░▒░▒░▒░▒▌ == COMMANDS (SYSOP) == ▐▒░▒░▒░▒░▒░▒░█
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
████████████████████████████████████████████████████████████████████████████████
KEYWORD: /COMMANDS/USERS/CLEAN/CLEAN-UP/CLEANUP
PROBLEM: How do I access clean-up mode?
To clean up the user list, you have to be in UltraMode (turned on and off with
Alt-F10). Once you're in UltraMode, select the USERS command.
████████████████████████████████████████████████████████████████████████████████
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
█░▒░▒░▒░▒░▒░▒▌ == DISPLAY == ▐▒░▒░▒░▒░▒░▒░█
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
████████████████████████████████████████████████████████████████████████████████
KEYWORD: /SEE/VIEW/43/50/EGA/VGA
PROBLEM: When viewing text files with SEE, I no longer switch to 43- or
50-line mode
The version of SEE that accompanies Sapphire is a custom version designed for
Sapphire. If you find a more recent version of SEE, don't install it in your
Sapphire directory.
████████████████████████████████████████████████████████████████████████████████
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
█░▒░▒░▒░▒░▒░▒▌ == DOORS == ▐▒░▒░▒░▒░▒░▒░█
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
████████████████████████████████████████████████████████████████████████████████
KEYWORD: /DOORS/OTHER BBS/INTERFACE
PROBLEM: How do I use doors that weren't specifically designed for Sapphire?
Several interface programs are available which will interface doors for one BBS
to another BBS. For example, the shareware programs SP2QBBS and DOORMASTER can
be used. Both of these programs may be obtained from our support system. If
you use them, please support the author's efforts by registering them.
───────────────────────────────────────────────────────────────────────────────
KEYWORD: /DOORS/REMOTE
PROBLEM: The door comes up but the users don't see anything
Here are a few things to check out:
1. Are you running a "FOSSIL" driver? If so, why? Does the door NEED the
fossil? Can you disable the fossil when it's not being used? If the door
documentation doesn't explicitly say that it needs a fossil driver, try
removing the fossil COMPLETELY before trying the door (i.e. reboot and
don't install it). Then, if that proves that the fossil was the cause of
the problem, read the fossil documentation to see if there is some way to
disable the fossil when it is not needed.
2. Does the door know which port it is supposed to be using? You may have to
use a door interface program (described above) to let it know.
3. Some programs (such as Pinnacle Software's Pyroto Mountain program) can
accept the port information on the command line, in which case you should
make sure that you are not pointing at the console. Taking Pyroto as an
example, if the command line specifies a port of 0 (zero), it means the
console. If it specifies a port address, it means the serial port.
───────────────────────────────────────────────────────────────────────────────
KEYWORD: /DOORS/RETURN
PROBLEM: How does Sapphire know we are coming back from a door?
When Sapphire creates the batch file EXTERNAL.BAT, it writes the part where it
starts itself back up as follows:
SAPPHIRE DOOR
This lets Sapphire know that it should not initialize the modem.
████████████████████████████████████████████████████████████████████████████████
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
█░▒░▒░▒░▒░▒░▒▌ == EVENTS == ▐▒░▒░▒░▒░▒░▒░█
█▒░▒░▒░▒░▒░▒░▌ ▐░▒░▒░▒░▒░▒░▒█
████████████████████████████████████████████████████████████████████████████████
KEYWORD: /EVENTS/RETURN
PROBLEM: How does Sapphire know we are coming back from a event?
When Sapphire creates the batch file EXTERNAL.BAT, it writes the part where it
starts itself back up as follows:
SAPPHIRE EVENT
This lets Sapphire know that it should not initialize the modem.
██████████████████████████████